INSERT INTO customers values (1, 'Smith', 'John', 'Stockton
Drive',
 'Exton', 'PA', 19341, mdsys.sdo_geometry(2001, 8307,
 mdsys.sdo_point_type(1,1,null),null,null));

This table has a numeric unique identifier (customer_id). In dealing with Bentley Map in a read/write setting, Oracle will be in control of assigning unique identifiers to the table’s rows. For new entries into the table it will use the sequence to generate a unique identifier. Note that the primary key here is explicitly named using the <table name>_pk naming convention, where pk is the acronym for "primary key". The <table name>_seq naming convention is used for sequences, with seq representing "sequence". This is not compulsory, but it helps in understanding the connection between the different entities in the database.

If a table with spatial data fits the extraction and read/write requirements, it should be possible to either:

• 'Discover' this table and define it as a feature and store it as part of a XFM schema using Bentley Geospatial Administrator. Bentley Map can then be loaded with this schema to extract/modify/post data from/to the table.

  OR

• Interactively connect to the Oracle database, and extract/modify/post data from/to the table on-the-fly.